A reusable prompt template that encodes senior UX thinking. Paste any PRD into Claude with this skill and get a structured analysis of gaps, ambiguities, and design questions in under 60 seconds.
A skill is a saved prompt template that encodes a specific type of thinking. You write it once, reuse it across projects, and share it across your team.
Version shared skills like code. Keep one strong sample input, one weak sample input, and the output shape you expect. When you revise the skill, rerun those checks before the team adopts the new version.
Four patterns used in this skill that make the difference between a prompt that works once and one that works reliably across every PRD.
// for meta-instructions// signals to Claude that these are rules governing how to run the skill — not content to reproduce in the output. Claude reads comment-style syntax as directives, not prose.// Do not summarise the PRD.
// Analyse it.
// Sections 1–5: 3–6 findings each.
// Section 6: exactly 2–3 principles.
// Reference requirement IDs
// (e.g. F-11, AC-03) wherever relevant.
// Prioritise by design impact,
// not document order.
You are a senior UX designer
reviewing a PRD.
Format: [Gap name]
→ [Req ID] → [What's needed]
Six structured sections, each targeting a different failure mode that PRDs commonly miss. Claude references specific requirement IDs throughout so every finding is traceable.
Paste this into Claude.ai (or any Claude interface) before your PRD text.
// PRD UX Analysis Skill // Use: Paste this before any PRD to surface UX gaps before design begins. You are a senior UX designer reviewing a product requirements document. Analyse the PRD below and produce a structured UX Analysis covering six sections: 1. UX GAPS Requirements that exist in the PRD but have no design guidance — where a design decision is being deferred to the designer without the information to make it. For each gap: name it, quote the relevant requirement ID, and describe what the designer needs to know before they can make this decision. 2. MISSING STATES Edge cases and states the PRD does not specify. For each: — Empty state (no data, first use, filtered to zero results) — Error state (API failure, sync failure, permission error) — Loading state (skeleton, progressive disclosure, timeout) — Zero-data state (newly created trial with no patients yet) — Permission conflict state (role sees partial data) Be specific about which features or screens each missing state applies to. 3. INTERACTION AMBIGUITIES Places where the PRD describes WHAT happens but not HOW. For each: quote the requirement, describe what is underspecified (trigger, feedback, transition, error handling, keyboard behaviour). Example: "F-14 says 'dropdown multi-select' but doesn't specify: does applying a filter update the table immediately or require a button press?" 4. ACCESSIBILITY FLAGS Requirements that are likely to be hard to meet accessibly as written. Reference WCAG 2.1 AA where relevant. Flag: — Colour-only status indicators without icon or text fallback — Interactive elements without specified keyboard navigation — Dynamic content updates without specified ARIA live region behaviour — Touch target size concerns for dense data tables 5. OPEN DESIGN QUESTIONS Questions the designer needs answered before wireframing begins. Format each as: [QUESTION] → [Why it matters for design] → [Who owns the answer] Prioritise by design impact. List no more than 8. 6. SUGGESTED UX PRINCIPLES Based on the user roles, workflow context, and constraints in this PRD, suggest 2–3 design principles that should guide this feature. Format: [Principle name]: [One sentence description] — [One concrete implication] // Instructions: // — Be specific. Reference requirement IDs (e.g. F-11, AC-03) wherever relevant. // — Prioritise findings by design impact, not document order. // — Sections 1–5 should have 3–6 findings each. Section 6 should have exactly 2–3 principles. // — Do not summarise the PRD. Analyse it.
Three ways to use it, depending on which tool you're in. The output is identical — the tool choice depends on what you want to do with it next.
Open claude.ai. Start a new conversation. Copy the prompt above → paste it → then paste your PRD below it → hit Enter. Claude will produce the full six-section analysis. Use this when you just need the analysis as a document to read and act on.
Save the skill prompt to a Claude Project alongside your design system docs, brand guidelines, and previous analyses. Now every team member who opens that Project gets Claude pre-loaded with your full design context. Ask: "Run the UX Analysis skill on the enrollment PRD" and it already knows your system.
Open the PRD file in Cursor. Type @PRD_Patient_Enrollment_Table.docx to attach it. Paste the skill prompt into the chat. The analysis will appear inline. Then immediately follow up: "Now generate a prototype that addresses the top 3 UX gaps you just identified." This turns analysis into design in one continuous session.
Paste the skill prompt into Claude Design followed by the PRD. After the analysis appears, follow up: "Based on the UX gaps you identified, design the loan application review table with those gaps resolved." The analysis and the prototype happen in the same canvas — no copy-pasting between tools.
In this workshop, a "skill" is a reusable prompt saved to a Claude Project — not the Claude Code developer feature. Here's how to go from idea to team-ready skill in a single conversation.
I want to create a reusable skill — a prompt template for a specific type of analysis. Goal: [what you want the skill to do — one sentence] Input type: [what you'll paste in — PRD, transcript, prototype HTML, spec doc] Output: [list the sections or findings you need] Audience: [who reads the output and what they do next] Constraints: [length, format, traceability, anything else] Write this as a structured skill prompt. Use // for meta-instructions, open with a role definition, name each output section explicitly with a count range for findings, include an example format for each finding type, and close with constraints as // comments. Make it ready to copy and paste.
Open a new Claude.ai conversation. Explain the analysis you want to run: what input you'll paste in, what you need back, who reads the output, and what they do with it. Claude will ask clarifying questions — answer them. The goal of this turn is to get the logic right, not the structure. Don't think about prompt format yet.
Once you've described the job, paste the starter prompt above into the same conversation. Claude already has your context from step 1 — the starter prompt tells it the structure to apply: role definition, // meta-instructions, named output sections with count ranges, and a format example for each finding type. It will produce a complete, copy-pasteable skill in one turn.
Open a new Claude.ai tab. Paste the draft skill + a real input document. Read the output critically against what you expected: Is the format right? Are findings specific or vague? Is a section missing? Is it too long? Go back to your drafting conversation — don't start a new one — and tell Claude exactly what to change. Two or three rounds is typical before a skill produces consistently good output.
In Claude.ai, open (or create) the Project you want to share the skill in. Open the project settings and paste the finished skill into the Project Instructions field. Every conversation opened in that project will now have the skill active — team members paste their input and run the analysis without ever touching the prompt text.
Invite team members to the project. Add a short // comment at the top of your instructions — one or two lines describing what the skill does, what input it expects, and what format it produces. Future maintainers (including you, six months from now) will thank you. When the skill needs updating, edit the project instructions directly — the change is live for everyone immediately.
The base skill works for any PRD. These variations tune it for specific research and design scenarios.
The skill becomes more powerful when the outputs accumulate. Here's how to build a knowledge base that amplifies everyone's work.
Phase 00 — UX Discovery. Design exploration and prototyping anchor the SDLC before requirements are formalized.
Scroll right to see full pipeline →